Method of enhancing call processing in a number portability environment

ABSTRACT

A method is provided which reduces post-dial delay in a number portability environment. In particular, a switching office which controls call routing to portable numbers (NPA-NXXs) contains a cache for which location routing number response information may be stored. The processing office concurrently checks the cache for LRN response information corresponding to the dialed number and launches a query to a number portability database. Thus, if the LRN response information in the cache is valid then the call will be routed in the timeliest manner. However, if either the cache does not have any LRN response information or the LRN response information in the cache proves not to be valid then, the switching office will have received the LRN response information from the database more quickly based on the concurrent launching of a query. Therefore, a more timely attempt at establishing a proper connection to the dialed number will occur thereby reducing post-dial delay.

BACKGROUND OF THE INVENTION

The present invention relates to a method for improving call processingin a number portability environment. Specifically, the present inventionrelates to a method for reducing post-dial delay while routing calls ina number portability context.

The U.S. telecommunications network is in a state of transition. In thenot too distant future it is expected that the monopoly held by localexchange carriers will be substantially altered and that CompetitiveAccess Providers (CAPs) will begin to provide competitive provide localexchange service. To accomplish this without creating an excessiveburden on customers who wish to receive service from a CAP, thecustomers will be able to change to a CAP without requiring the changeof a telephone number. This type of flexibility is referred to asservice provider number portability. It enables the subscriber to changehis or her service provider while maintaining the same directory number.The public policy goal is to ensure that there is no performancedegradation between carriers.

It is also expected that subscribers will be able to move betweengeographic locations within some reasonably defined region, for example,within the same LATA, while retaining the same telephone number. This isreferred to as geographic portability. In this case the subscriber mayor may not change service providers.

An additional type of portability relates to a customer's desire tochange the type of service in use. For instance, a customer may changefrom Plain Old Telephone Service (POTS) to IDSN service and wish tomaintain the same directory number. This is referred to as serviceportability.

AT&T has already proposed a system for providing both service providerand geographic number portability. This system uses a mechanism referredto as the Location Routing Number (LRN) mechanism. In the LocationRouting Number mechanism during call processing a local switch analyzesthe dialed number to determine both whether that number is from aportable NPA-NXX, that is, whether at least one NPA-NXX-XXXX has portedto another local switch, and whether the call is interswitch, that iswhether or not a different local switch serves the destination number.If the number's NPA-NXX is determined to be portable and if the call isinterswitch then the network switch launches a query to a numberportability (NP) database. If the number has been ported the databasethen returns a location routing number (LRN) of the recipient switch towhich the dialed number has been ported. The querying switch receivesthe LRN and uses it to route the call to its correct destination.

If the number has not been ported then the NP database returns thedialed number (DN) and the switch appropriately routes the call.

Examples of the call flow in the LRN mechanism are illustrated in priorart FIGS. 1 and 2.

FIG. 1 illustrates call processing in an LRN mechanism when a call froma calling party A to a called party B is a local interswitch call. Inthe example, in step 1 party A (having number 212-949-3001) dials212-984-3001, the number assigned to party B. The end office (EO) 10 oflocal service provider (LSP) 1 receives the dialed number and determinesthat the number's NPA-NXX is portable. EO 10 then launches a query viaSignaling Transfer Point (STP) 20 to a number portability (NP) database30. The query includes the dialed number received by EO 10. The NPdatabase 30 then returns the location routing number to the EO 10. Thefirst six digits of the LRN are indicative of a particular LSP EQ. TheLRN is populated in the Called Party Number ISUP (ISDN user port)parameter of the Initial Address Message (IAM) of the Signaling System 7(SS7) protocol. The dialed number is placed in the generic addressparameter (GAP). Furthermore, an indicator is set to represent the factthat the routing information is based on a query to the database. Whenthe EO 10 receives this information it then routes the call to thetandem switch 40 based on the first six digits of the LRN. The tandemswitch then routes the call to the end office of the LSP3, 50, to whichcalled party B is presently ported rather than the end office of LSP 2,60, to which the called party B was previously ported. Finally, in afifth step the EO 50 presently serving the ported subscriber recognizesits own LRN and obtains the dialed number from the generic addressparameter and uses that information to complete the call to station B.In summary, for interswitch calls to portable NPA-NXXs the end officeswitch 10 launches a query to a database to obtain routing informationfor the end office which is servicing the ported customer.

FIG. 2 illustrates a similar situation in the context of an interLATAcall where the call must be serviced by an Inter-Exchange Carrier (IXC).Like elements in FIGS. 1 and 2 bear identical reference numerals. Inthis instance the EO 10 determines that the call is an interLATA calland therefore sends the dialed number information to the IXC originatingswitch 15. The IXC recognizes the dialed number as pertaining to aportable NPA-NXX and generates a query using the dialed number(212-984-3001 in the illustrated example). The query goes to theSignaling Transfer Point (STP) 25 and is forwarded to a numberportability (NP) database 35. The NP database 35 could be a nationaluniversal database. The distinctions between the database 35 of FIG. 2and the database 30 of FIG. 1 could correspond to the differencesbetween the national and local databases described in co-pendingapplication Ser. No. 08/861,756, the entire disclosure of which isincorporated by reference hereto. As in the case of the query responsein FIG. 1, if the number has been ported, the NP database 35 providesthe LRN information associated with the dialed number. The originatingIXC switch formats an ISUP IAM and places the LRN information (here212-484-9999) in the called party number parameter. The dialed number isstored in the generic address parameter and the M-bit of the ForwardCall indicator (FCI) is set to indicate that the NP database 35 wasqueried. The originating IXC 15 then routes the call to terminating IXCswitch 45 based on the first six digits of the LRN. The terminating IXCswitch determines a routing path to the EO 55 of LSP 3, 50, based on thefirst six digits of the LRN. The end office 55 recognizes its own LRNand then obtains the dialed number from the GAP and completes the callto station B.

In the two examples described, a query is launched to the database,either local database 30 or national database 35 each time aninterswitch call to a portable NPA-NXX is detected. As a result, thesystem generates a large number of queries. In fact, for a frequentlydialed number a query related to that dialed number may have beenprocessed only a few minutes or even perhaps just a few seconds,earlier. These queries come at a cost. First, there is the load on thesystem in query traffic. Then there is the processing to be done at theNP database to respond to all queries. Finally, there is a built-indelay for processing all interswitch calls to portable NPA-NXXs since aquery must be launched and processed before the call is routed. In aco-pending application by the same inventors filed on the same date asthe present application it is proposed to employ a cache at theswitching office that launches the database query. The cache is checkedbefore a query is launched so that if LRN response information is in thecache there is no query unless upon attempting a connection using theLRN response information in the cache the attempt fails because thecached information is incorrect. That deployment of a cache reducesqueries. However, the inventors have also noted that post-dial delay, aphenomenon of concern to service providers, can be exacerbated bydelaying the launch of database queries until an attempt to connectusing cached LRN response information fails. The communication industryhas recognized that the delay experienced by a calling party aftercompleting the dialing of a number can have a significant impact on theperception of the service provided. Too long a delay may present a veryclear indication that the called party is now ported to a differentservice provider and may suggest that there is a degradation of serviceas a result of the porting. There is no agreement within the industryregarding acceptable values for post-dial delay. It would therefore bebeneficial to reduce post-dial delay wherever possible to avoid theappearance of service degradation to the calling party.

SUMMARY OF THE INVENTION

The present invention is directed to a method for enhancing callprocessing in a number portability environment. In particular, theinvention reduces post-dial delay enabling faster attempts at routingcalls to portable numbers.

In accordance with the present invention a cache memory is associatedwith the local exchange or inter-exchange carrier switch responsible forprocessing the call to the portable NPA-NXX. The cache memory stores,for a limited period of time, LRN response information received from thenumber portability database in response to queries launched regardingdialed numbers associated with portable NPA-NXXs. At the same time theswitch checks the cache upon receipt of a dialed number associated witha portable NPA-NXX to determine if the cache contains LRN responseinformation for that number, it launches a query to a number portabilitydatabase. If the cache contains such response information, then thelocal exchange or IXC attempts to route the call based on the cached LRNresponse information. If the cache does not contain information relatingto the dialed number, or if the attempt to route the call based on LRNresponse information in the cache is unsuccessful, then LRN responseinformation received from the earlier query is used for routing.

BRIEF DESCRIPTION OF THE DRAWINGS

FIGS. 1 and 2 illustrate call flows for known number portabilitysystems.

FIGS. 3 to 5 illustrate call flows in accordance with an embodiment ofthe present invention.

FIG. 6 illustrates the format of parameter information useable inconnection with an embodiment of parameter information useable inconnection with an embodiment of the present invention.

FIG. 7 illustrates call flow in a modification of an embodiment of thepresent invention.

DETAILED DESCRIPTION

Overview

In accordance with an embodiment of the present invention, a cache isassociated with the switching office which is responsible for launchingqueries to a number portability database. Every time the switchingoffice receives a portable number it launches a query to the numberportability database and checks the cache to determine whether locationrouting number response information for a received dialed number isavailable in the cache. This checking operation is performedconcurrently with the launching of a query to the number portabilitydatabase. If LRN response information is found in the cache, the switchwill attempt to complete the call. This will increase the speed withwhich calls are processed since it is quicker to access LRN responseinformation from a cache associated with the switch than it is to waitto receive data back from the number portability database afterlaunching a query. If, however, the attempt to connect the call fails,the switch should have already received or is about to receive the LRNresponse information from the NP database. Thus, another attempt toconnect the call will be made with a substantially shorter delay than ifthe switch waited until notice of failure to connect before launchingthe query. The result is a reduction of post dial delay. This reductionenhances the calling party's perception of the call processingoperation. Before describing the call flows for implementation of thepresent invention it is helpful to understand the terminology typicallyused in the field of number portability. The following glossary isuseful in that regard.

Local Service Provider (LSP): A local service provider refers to theprovider of local access functionality to an end customer. LSPs aresynonymous with local exchange carriers (LECs), alternate local exchangecarriers, competitive access providers, and other terms that may be usedto refer to providers of local access.

Numbering Plan Area (NPA): The initial group of three digits of a NorthAmerican numbering plan (NANP) number. The format of NPA is NXX where Nis any digit from 2 to 9 and X is any digit from 0 to 9.

Number Portability: Gives the subscriber the ability to move from oneend office (i.e., switch) to another and keep its original directorynumber (DN). There are three types of number portability as described inthe background section of the application. FCC and state regulatoryactivities primarily deal with the implementation of service providernumber portability.

Default LSP: In today's environment, the local exchange routing guide(LERG) identifies which NPA-NXXs are assigned to which LSP end offices.The LSP appearing in the LERG is the default LSP for an NPA-NXX and thedefault LSP for the line numbers is that NPA-NXX.

Default Routing: Refers to routing a call to the default LSP based onthe first 6 digits (NPA-NXX) of a NANP number.

Ported Number: A ported number is an end customer's number which is nolonger served by the default local service provider as defined in thelocal exchange routing guide.

Location Routing Number: A location routing number is an identifier ofan LSP end office. The LRN of an LSP end office is defined as a 10 digitnumber of the format NPA-NXX-XXXX such that the first 6 digits is anNPA-NXX assigned (in the local exchange routing guide) to the LSP endoffice. Also, a 6 digit translation on the NPA-NXX of the LRN willresult in routing calls to the LSP end office.

Number Portability (NP) Database: An NP database is a database whichstores number portability data, such as the LRNs for ported numbers.Switches will query a number portability database with a dialed numberto obtain number portability information for the dialed number.

Destination Number: For routing a call the number used to query thenumber portability database will be referred to as the destinationnumber. The destination number can be the number received from theincoming called party number (CdPN) parameter (e.g., dialed number) orthe number derived after service processing (e.g., the translated numberafter 800 service processing has been applied).

Calling Party Number (CPN) Parameter: An existing SS7 ISUP (ISDN userpart) initial address message (IAM) parameter which currently carriesthe calling party number.

Called Party Number (CdPN) Parameter: An existing SS7 ISUP initialaddress message parameter which currently carries the destinationnumber. Switches use the number populated in this parameter to determinehow to route the call.

Generic Address Parameter (GAP): The GAP is an existing optional SS7ISUP initial address message parameter. Multiple GAPs can be defined fora call. Within the LRN approach, the dialed number is populated in theGAP when the LRN is populated in the Called Party Number parameterinstead of the called party number.

Bits M and N of a forward call indicator: Bits M and N have been definedas associated with number portability in the current invention.

Portable NPA-NXX: An NPA-NXX is defined as portable if it has one ormore ported numbers. That is, destination numbers with a portableNPA-NXX are no longer associated with a unique LSP.

Number Portability (NP) Capable/Non NP Capable Switch: An NP capableswitch is a switch which has the capability to support the LRN solutionfor number portability. A non-NP capable switch is a switch which doesnot have the capability to support the LRN solution for numberportability. A non-NP capable switch can have numbers ported to and fromit and have an LRN assigned to it. However, it does not have thecapability to query a number portability database nor to recognize itsown LRN and retrieve a ported destination number from the genericaddress parameter.

Description of the Proposed Call Flows

For purposes of the following discussion the assumption will be that atsome time prior to the call being processed a called party B was servedby end office 160 of local service provider 2 and has been ported by theend office 150 of local service provider 3. The shift between serviceproviders could constitute either geographic restricted portability ofthe calling party B, or service provider portability, that is a changeto a different local service provider, or both. In either portabilitycircumstance the ported party B is served by a different end office andhence a different "service provider".

FIG. 3 illustrates the circumstance where the calling party A, beingserviced by its local service provider can call the (ported) calledparty B with LRN response information being available to the end officeof the LSP 1. More specifically, calling party A dials the portednumber, here 212-984-3001. The end office 110 receives the number anddetects that 212-984 is a portable NPA-NXX and that the call isinterswitch, i.e., end office 110 does not "serve" called party B. Theend office then does two things. It launches a query to numberportability database 140 via Signaling Transfer Point (STP) 130. The endoffice also checks cache 100 to determine whether it contains locationrouting number response information corresponding to the dialed number.In this call processing sequence, the cache does include the LRNresponse information including the LRN of 212-484-9999. Thus, the endoffice 110 places the LRN in the called party IAM parameter and placesthe dialed number in the generic address parameter. A query bitindicator, bit N of the FCI is also set in the IAM message to indicatethat the LRN response information has not come from the numberportability database. The end office then routes the call via tandemswitch 120 to the end office 150 of LSP 3 identified by the LRN from thecache. The LSP 3 end office then recognizes its own LRN in the CdPNparameter, obtains the dialed number from the generic address parameter,and completes the call to station B. In this configuration then, incomparison to the known LRN mechanism described above, a cache memory isprovided in association with the end office 100 and is checked todetermine if call routing can be done before receiving the LRN responseinformation from the NP database.

The call flow illustrated in FIG. 4 relates to that circumstance wherethe cache memory does not contain LRN response information for thedialed number. Here again the calling party dials 212-984-3001. Endoffice 110 detects that the NPA-NXX is portable, launches a query to NPdatabase 140, and checks cache 100 to determine if the cache containsany LRN response information relating to the dialed number. In thisinstance the end office does not detect any valid information in thecache relating to the dialed number. The term "valid information" isused to indicate that information within the cache may be deemed to beunreliable after some specified period of time. Therefore, even ifresponse information exists in the cache for a particular called number,those entries may have been in the cache for such a period of time thatstatistically they are no longer reliable and are therefore treated asinvalid pieces of information. More information regarding theconsideration given to LRN information within the cache will be providedbelow. Continuing with the call flow of FIG. 4, since the cache does notcontain any information regarding the dialed number, end office 110awaits a response to the launched query. The NP database returns LRNresponse information 212-484-9999. As with the call flow of FIG. 3, thecalled party number parameter is populated with the LRN while thegeneric address parameter is populated with the dialed number. In thisinstance however, the query indicator is adjusted to reflect the factthat the LRN response information comes from the number portabilitydatabase. The LRN response information is then used by end office 110 toroute the call to the end office to which station B is ported asindicated by the LRN, that is LSP 3 end office 150. That LSP thenrecognizes its own LRN and obtains the dialed number information fromthe generic address parameter and completes the call to station B.

In addition to routing the call using the LRN information from thedatabase, the LRN response information is also provided to the cache 100in association with the dialed number. The cache entry is designated asa valid entry and is considered as such for some set period of time. Forinstance, when the results of a query to the number portability databaseare stored in the local cache, a timer could be set that defines themaximum time interval for which that cached information may beconsidered as current or valid. At the expiration of this timer theentry from the local cache should be flushed. In the event that thecache is full at the time LRN response information is provided for aquery and a new entry needs to be stored, the oldest cache entry (thatis, the entry whose local cache timer is closest to expiration) must beflushed. It would be beneficial if the timer is refreshed/reset to themaximum timer value every time there is a successful hit in the localcache for this dialed number. This will tend to ensure that theinformation for the numbers that are dialed frequently will be readilyavailable in the local cache thereby reducing post dial delay for callsto such numbers.

The situation may arise where the LRN response information in the cachemay be still considered timely within the criteria described above butin fact, inaccurately reflects the end office which serves the calledparty B. FIG. 5 of the present application provides a call flow diagramfor number portability processing in that instance. In this instance itwill be assumed that the cache 100 stores LRN response informationindicating that a called party B is ported to LSP 2 of end office 170and that LRN response information is still considered timely in thecache. Nonetheless, calling party B has been ported to end office 150for LSP 3. In this circumstance then the end office 110, upon detectingthe NPA-NXX to be portable and the call to be interswitch, examines thecache and determines that LRN response information is present in thecache. In this instance the LRN response information is the LRN for endoffice 170, 212-984-9999. This information is placed in the called partynumber field and the dialed number is placed in the generic addressnumber parameter field. The end office 110 then attempts to route thecall to the end office corresponding to or identified by the calledparty number, in this instance end office 170 corresponding to LSP 2.The called party B is no longer served by end office 170. The call tothat end office is cleared and a code is sent back to indicate that theend office 170 is not ported to the dialed number. Since the end office110 launched a query to the number portability database at the same timeit checked the cache, it will have either received or is about toreceive the LRN response information from the NP database at the timethe code is received. The more authoritative LRN response informationfrom the NP database, in this example 212-490-9999, is then populated inthe called party number parameter and the generic address parametercontinues to reflect the dialed number, 212-984-3001. In this instancethe number portability query indicator is changed to reflect that thenumber portability database has been queried and that the LRN responseinformation comes from a more authoritative source than the local cache.

FIG. 6 illustrates the format of the FCI parameter of the IAM. Ofparticular significance in this format are bits M and N. Bit M is usedby the conventional LRN approach to indicate whether an NP databasequery has been performed. Of more significance to the current inventionis the status of bit N which indicates the relative authority to beascribed to the CdPN namely that the information in the IAM has beenobtained from the local cache rather than from the number portabilitydatabase.

The call flows described in connection with FIGS. 3 to 5 all relate toproviding a cache in the end office of the local service provider 1associated with the calling party A and launching a query to thedatabase concurrently with checking the cache. Thus, there areimprovements over the system illustrated in FIG. 1. It is also presumedthat one of ordinary skill in the art would be able to recognizeemploying the cache memory at the switching office of the inter-exchangecarrier which is determined to be responsible for call processing as inthe example of FIG. 2. Here the cache would then be associated with theIXC originating switch, for example, 15 in FIG. 2. The decision makingtree however, would be very similar to the present invention and wouldprovide that for every interswitch call to a portable NPA-NXX, a queryis launched to a NP database while the switch checks a local cache forany location routing number response information. Then if either thecache does not contain LRN response information or, in a worst casescenario, if an IAM clearing message indicates that the LRN responseinformation retrieved from the cache is incorrect the number portabilitydatabase response information is available from the parallel.

One skilled in the art would recognize that the present invention wouldstill be effective even if the switch did not launch a query for eachand every portable NPA-NXX. It is possible that a class of portableNPA-NXXs may not experience unacceptable post dial delay even if a queryis only launched after checking the cache or receiving a notice offailure to connect. In that instance the switch might concurrently checkthe cache and launch queries only for those portable numbers not in thatclass.

FIG. 7 illustrates a modification of the present invention illustratedin FIGS. 3 to 5 wherein the calling party is associated with a localservice provider 1 which hands off the call to a homogeneous sub-networkof LRN capable switches via MF signaling. In that instance, it is theLSP2 end office which would contain the cache. Then that end officewould launch a query to the number portability database and would checkthat cache for LRN response information. Subsequent call processingwould be the same as described above.

The present invention can be implemented on a switch such as a 4ESS or5ESS from Lucent Technologies with modifications to call processingsoftware that reflect the call flows described herein.

The present invention provides a unique call processing scheme whichreduces the post dial delay that might otherwise arise in processingcalls to portable numbers. Thus calls to portable numbers, regardless ofwhether the change in service provider relates to limited geographicportability or simply selecting a different access provider, can beprocessed more quickly.

What is claimed is:
 1. A method for reducing post dial delay in anetwork providing a number portability environment, the methodcomprising the steps of:receiving a dialed number; recognizing saiddialed number as a portable number; checking a cache to determine if alocation routing number for said portable number has been cached; whilesaid step of checking said cache is performed, querying a database thatcorrelates portable numbers to respective location routing numbers todetermine a location routing number for said portable number; if saidstep of checking determines a location routing number to be cached forsaid portable number then attempting to route the call to said portablenumber using location routing number response information from saidcache; receiving location routing number response informationcorresponding to said portable number from said database in response tothe step of querying, and if said step if checking determines no validlocation routing number to be cached for said portable number, thenattempting to route the call to said portable number using said locationrouting number response information received from said database.
 2. Themethod of claim 1 further comprising the step of updating said cacheusing the location routing number response information received fromsaid database.
 3. The method of claim 1 comprising the further step ofreceiving a notification of failure to complete the call to saidportable number after attempting to route the call using said locationrouting number from said cache.
 4. The method of claim 3 comprising thefurther step of attempting to route the call to said portable numberusing said location routing number response information from saiddatabase prior to receiving said notification if the location routingnumber response information from said database differs from the locationrouting number response information from said cache.
 5. The method ofclaim 4 further comprising the step of updating said cache using thelocation routing number response information received from saiddatabase.
 6. In a communication system in which a telephone number isportable between at least two service providers, a method for reducingpost-dial delay for an originating party calling the portable number,the method comprising the steps of:receiving a dialed number at a localoffice associated with the originating party; checking a cacheassociated with said local office for a location routing numberassociated with said dialed number; concurrent with said step ofchecking, launching a query to a database for obtaining a locationrouting number for said dialed number; receiving said location routingnumber from said database in response to said query; and if said step ofchecking determines a location routing number to be cached for saidportable number, then, prior to receiving a response from said database,attempting to route the call to said portable number using said locationrouting number from said cache.
 7. The method of claim 6 comprising thefurther step of updating said cache using said location routing numberreceived from said database.
 8. The method of claim 6 wherein a locationrouting number from said cache corresponds to a first service providerand a location routing number from said database corresponds to a secondservice provider.
 9. The method of claim 8 wherein the first and secondservice providers correspond to first and second local switching officesrespectively.
 10. The method of claim 8 wherein the first and secondservice providers correspond to first and second carriers respectively.11. In a communication system in which a telephone number is portablebetween at least two service providers, a method for reducing post-dialdelay for an originating party calling the portable number, the methodcomprising the steps of:receiving a dialed number; checking a cache fora location routing number associated with said dialed number; concurrentwith said step of checking, launching a query to a database forobtaining a location routing number for said dialed number; receivingsaid location routing number from said database in response to saidquery; and if said step of checking determines a location routing numberto be cached for said portable number, then, prior to receiving aresponse from said database, attempting to route the call to saidportable number using said location routing number from said cache.